Playback queue control

ABSTRACT

Example techniques involve control of a media playback system involving multiple zones. A control application may include different control interfaces for respective zones of the multiple zones. A control interface for a given zone may include transport controls to control playback in the zone, volume controls to control zone volume level, and an indication of media playing back in the zone. A user may utilize swipe inputs to switch between the control interfaces in order to control different zones.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority under 35 U.S.C. § 120 to, and is acontinuation of, U.S. non-provisional patent application Ser. No.16/295,390, filed on Mar. 7, 2019, entitled “Playback Queue Control,”which is incorporated herein by reference in its entirety.

U.S. non-provisional patent application Ser. No. 16/295,390 claimspriority under 35 U.S.C. § 120 to, and is a continuation of, U.S.non-provisional patent application Ser. No. 16/150,011, filed on Oct. 2,2018, entitled “Playback Queue Control for a Zone-Based Media PlaybackSystem,” and issued as U.S. Pat. No. 10,270,612 on Apr. 13, 2019, whichis incorporated herein by reference in its entirety.

U.S. non-provisional patent application Ser. No. 16/295,390 claimspriority under 35 U.S.C. § 120 to, and is a continuation of, U.S.non-provisional patent application Ser. No. 13/247,775, filed on Sep.28, 2011, entitled “Methods and Apparatus To Change Control Contexts ofControllers,” which is incorporated herein by reference in its entirety.

FIELD OF THE DISCLOSURE

The disclosure is related to consumer electronics and, moreparticularly, to methods and apparatus to change control contexts ofcontrollers.

BACKGROUND

Technological advancements have increased the accessibility of musiccontent, as well as other types of media, such as television content,movies, and interactive content. For example, a user can access audio,video, or both audio and video content over the Internet through anonline store, an Internet radio station, an online music service, anonline movie service, and the like, in addition to the more traditionalavenues of accessing audio and video content. Demand for such audio andvideo content continues to surge. Given the high demand, technology usedto access and play such content has likewise improved.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and advantages of the presently disclosed technologyare better understood with regard to the following description, appendedclaims, and accompanying drawings where:

FIG. 1 shows an illustration of an example system in which embodimentsof the methods and apparatus disclosed herein may be implemented;

FIG. 2A shows an illustration of an example zone player having abuilt-in amplifier and speakers;

FIG. 2B shows an illustration of an example zone player having abuilt-in amplifier and connected to external speakers;

FIG. 2C shows an illustration of an example zone player connected to anA/V receiver and speakers;

FIG. 3 shows an illustration of an example controller;

FIG. 4 shows an internal functional block diagram of an example zoneplayer;

FIG. 5 shows an internal functional block diagram of an examplecontroller;

FIG. 6 shows an internal functional block diagram of an exampleimplementation of the control context module of FIG. 5;

FIG. 7 is a screenshot of an example user interface associated with theexample control context module of FIGS. 5 and/or 6;

FIG. 8 is a series of screenshots illustrating a transition of theexample user interface of FIG. 7;

FIG. 9 is a flow diagram representative of example machine readableinstructions that can be executed to implement the example controlcontext module of FIGS. 5 and/or 6;

FIG. 10 shows an internal functional block diagram of an exampleimplementation of the queue position placement (QPP) module of FIG. 5;

FIG. 11 is a screenshot of a portion of an example user interfaceassociated with the example QPP module of FIGS. 5 and/or 11;

FIG. 12 is a screenshot of a portion of an example user interfaceassociated with the example QPP module of FIGS. 5 and/or 11;

FIG. 13 is a screenshot of a portion of an example user interfaceassociated with the example QPP module of FIGS. 5 and/or 11;

FIG. 14 is a screenshot of a portion of an example user interfaceassociated with the example QPP module of FIGS. 5 and/or 11;

FIG. 15 is a screenshot of a portion of an example user interfaceassociated with the example QPP module of FIGS. 5 and/or 11;

FIG. 16 is a screenshot of a portion of an example user interfaceassociated with the example QPP module of FIGS. 5 and/or 11;

FIG. 17 is a flow diagram representative of example machine readableinstructions that can be executed to implement the example QPP module ofFIGS. 5 and/or 11;

In addition, the drawings are for the purpose of illustrating exampleembodiments, but it is understood that the present disclosure is notlimited to the arrangements and instrumentality shown in the drawings.

DETAILED DESCRIPTION I. Overview

Embodiments of the methods and apparatus disclosed herein enable a userto easily and conveniently change control contexts of a controller.

An example embodiment of an apparatus implemented in accordance with thepresent disclosure includes a touch screen to display a user interface;a controller to control a first physical playback device of a first zonewhen in a first control context and to control a second physicalplayback device of a second zone when in a second control context; aswipe detector to monitor a designated area of a user interface for aswipe of the touch screen; and a context changer to change thecontroller from operating in the first control context to operating inthe second control context in response to a detected swipe.

In some embodiments, the apparatus further includes a user interfacecommunicator to facilitate a change in a display of the designated areain response to the detected swipe.

In some embodiments, the display includes information related to acurrently selected media item in the first or second zone.

In some embodiments, the display includes an identifier of the firstzone when in the first control context.

In some embodiments, the user interface includes an indicator reflectiveof a list of control contexts in which the controller operates.

In some embodiments, the first and second physical playback devices areplayback devices capable of generating a media presentation.

In some embodiments, the first and second zones are part of an in-homewhole house media system.

An example method implemented in accordance with the present disclosureincludes monitoring a designated area of a user interface for a swipe ofa touch screen; and changing a controller from operating in a firstcontrol context to operating in a second control context in response toa detected swipe, wherein the controller controls a first physicalplayback device of a first zone when in the first control context, andwherein the controller controls a second physical playback device of asecond zone when in the second control context.

In some embodiments, the method further includes facilitating a changein a display of the designated area in response to the detected swipe.

In some embodiments, the display includes information related to acurrently selected media item in the first or second zone.

In some embodiments, the display includes an identifier of the firstzone when in the first control context.

In some embodiments, the user interface includes an indicator reflectiveof a list of control contexts in which the controller operates.

In some embodiments, the first and second physical playback devices areplayback devices capable of generating a media presentation.

In some embodiments, the first and second zones are part of an in-homewhole house media system.

An example tangible machine-readable medium has instructions storedthereon implemented in accordance with the present disclosure that causea machine to at least monitor a designated area of a user interface fora swipe of a touch screen; and change a controller from operating in afirst control context to operating in a second control context inresponse to a detected swipe, wherein the controller controls a firstphysical playback device of a first zone when in the first controlcontext, and wherein the controller controls a second physical playbackdevice of a second zone when in the second control context.

In some embodiments, the instructions cause the machine to facilitate achange in a display of the designated area in response to the detectedswipe.

In some embodiments, the display includes information related to acurrently selected media item in the first or second zone.

In some embodiments, the display includes an identifier of the firstzone when in the first control context.

In some embodiments, the first and second physical playback devices areplayback devices capable of generating a media presentation.

In some embodiments, the first and second zones are part of an in-homewhole house media system.

Although the following discloses example methods, apparatus, systems,and articles of manufacture including, among other components, firmwareand/or software executed on hardware, it should be noted that suchmethods, apparatus, systems, and/or articles of manufacture are merelyillustrative and should not be considered as limiting. For example, itis contemplated that any or all of these firmware, hardware, and/orsoftware components could be embodied exclusively in hardware,exclusively in software, exclusively in firmware, or in any combinationof hardware, software, and/or firmware. Accordingly, while the followingdescribes example methods, apparatus, systems, and/or articles ofmanufacture, the examples provided are not the only way(s) to implementsuch methods, apparatus, systems, and/or articles of manufacture.

When any of the appended claims are read to cover a purely softwareand/or firmware implementation, at least one of the elements in at leastone example is hereby expressly defined to include a tangible mediumsuch as a memory, DVD, CD, Blu-ray, etc., storing the software and/orfirmware.

These embodiments and many additional embodiments are described morebelow. Further, the detailed description is presented largely in termsof illustrative environments, systems, procedures, steps, logic blocks,processing, and other symbolic representations that directly orindirectly resemble the operations of data processing devices coupled tonetworks. These process descriptions and representations are typicallyused by those skilled in the art to most effectively convey thesubstance of their work to others skilled in the art. Numerous specificdetails are set forth to provide a thorough understanding of the presentdisclosure. However, it is understood to those skilled in the art thatcertain embodiments of the present disclosure may be practiced withoutcertain, specific details. In other instances, well known methods,procedures, components, and circuitry have not been described in detailto avoid unnecessarily obscuring aspects of the embodiments.

Reference herein to “embodiment” means that a particular feature,structure, or characteristic described in connection with the embodimentcan be included in at least one example embodiment of the invention. Theappearances of this phrase in various places in the specification arenot necessarily all referring to the same embodiment, nor are separateor alternative embodiments mutually exclusive of other embodiments. Assuch, the embodiments described herein, explicitly and implicitlyunderstood by one skilled in the art, may be combined with otherembodiments.

II. Example Environment

Referring now to the drawings, in which like numerals may refer to likeparts throughout the figures. FIG. 1 shows an example systemconfiguration 100 in which one or more of the method and/or apparatusdisclosed herein may be practiced or implemented. By way ofillustration, the system configuration 100 represents a home withmultiple zones. Each zone, for example, represents a different room orspace, such as an office, bathroom, bedroom, kitchen, dining room,family room, home theater room, utility or laundry room, and patio.While not shown here, a single zone may cover more than one room orspace. One or more of zone players 102-124 are shown in each respectivezone. A zone player 102-124, also referred to as a playback device,multimedia unit, speaker, etc., provides audio, video, and/oraudiovisual output. A controller 130 (e.g., shown in the kitchen forpurposes of illustration) provides control to the system configuration100. The system configuration 100 illustrates an example whole houseaudio system, though it is understood that the technology describedherein is not limited to its particular place of application or to anexpansive system like a whole house audio system 100 of FIG. 1.

FIGS. 2A, 2B, and 2C show example illustrations of zone players 200-204.The zone players 200-204 of FIGS. 2A, 2B, and 2C, respectively, maycorrespond to any of the zone players 102-124 of FIG. 1. While certainembodiments provide multiple zone players, an audio output may begenerated using only a single zone player. FIG. 2A illustrates a zoneplayer 200 including sound producing equipment 208 capable of generatingsound or an audio output corresponding to a signal received (e.g.,wirelessly and/or via a wired interface). The sound producing equipment208 of the zone player 200 of FIG. 2A includes a built-in amplifier (notshown in this illustration) and speakers (e.g., a tweeter, a mid-rangedriver, and/or a subwoofer. In certain embodiments, the zone player 200of FIG. 2A may be configured to play stereophonic audio or monauralaudio. As described in greater detail below, in some embodiments, theexample zone player 200 of FIG. 2A can also transmit a second signal to,for example, other zone player(s) in the same or different zone(s),speaker(s), receiver(s), etc. Transmission of the second signal may bepart of, for example, a system in which multiple zone players, speakers,receivers, etc. form a network to, for example, present media content ina synchronization or distributed manner.

The example zone player 202 of FIG. 2B includes a built-in amplifier(not shown in this illustration) to power a set of detached speakers210. The speakers 210 of FIG. 2B may include, for example, any type ofloudspeaker. The zone player 202 of FIG. 2B can communicate a signalcorresponding to audio content to the detached speakers 210 via wiredand/or wireless channels. Instead of receiving and generating audiocontent as in FIG. 2A, the zone player 202 of FIG. 2B receives the audiocontent and transmits the same (e.g., after processing the receivedsignal) to the detached speakers 210. Similar to the example zone player200 of FIG. 2A, in some embodiments the zone player 202 can transmit asecond signal to, for example, other zone player(s) in the same ordifferent zone(s), speaker(s), receiver(s), etc.

The example zone player 204 of FIG. 2C does not include an amplifier,but allows a receiver 214, or another audio and/or video type devicewith built-in amplification, to connect to a data network 128 of FIG. 1and to play audio received over the data network 128 via the receiver214 and a set of detached speakers 216. In addition to the wiredcouplings shown in FIG. 2C, the detached speakers 216 can receive audiocontent via a wireless communication channel between the detachedspeakers 216 and, for example, the zone player 204 and/or the receiver214. In some embodiments the zone player 202 can transmit a secondsignal to, for example, other zone player(s) in the same or differentzone(s), speaker(s), receiver(s), etc.

Example zone players include a “Sonos® S5,” “Sonos Play:5,” “ZonePlayer120,” and “ZonePlayer 90,” which are offered by Sonos, Inc. of SantaBarbara, Calif. A zone player may also be referred to herein as aplayback device, and a zone player is not limited to the particularexamples illustrated in FIGS. 2A, 2B, and 2C. For example, a zone playermay include a wired or wireless headphone. In another example, a zoneplayer might include a subwoofer. In an example, a zone player mayinclude or interact with a docking station for an Apple iPod™ or similardevice. In some embodiments, a zone player may relay one or more signalsreceived from, for example, a first zone player to another playbackdevice. In some embodiments, a zone player may receive a first signaland generate an output corresponding to the first signal and,simultaneously or separately, may receive a second signal and transmitor relay the second signal to another zone player(s), speaker(s),receiver(s), etc. Thus, an example zone player described herein can actas a playback device and, at the same time, operate as a hub in anetwork of zone players. In such instances, media content correspondingto the first signal may be different from the media contentcorresponding to the second signal.

FIG. 3 shows an example illustration of a wireless controller 300 in adocking station 302. The controller 300 may correspond to thecontrolling device 130 of FIG. 1. The controller 300 is provided with atouch screen 304 that allows a user to interact with the controller 300to, for example, retrieve and navigate a playlist of audio items,control operations of one or more zone players, and provide overallcontrol of the system configuration 100. In certain embodiments, anynumber of controllers may be used to control the system configuration100. In certain embodiments, there may be a limit on the number ofcontrollers that can control the system configuration 100. Thecontrollers might be wireless like wireless controller 300 or wired tothe data network 128. Furthermore, an application running on anynetwork-enabled portable devices, such as an iPhone™, iPad™, Android™powered phone, or any other smart phone or network-enabled device may beused as a controller by connecting to the data network 128. Anapplication running on a laptop or desktop PC or Mac may also be used asa controller. Example controllers include a “Sonos® Controller 200,”“Sonos® Controller for iPhone,” “Sonos® Controller for iPad,” “Sonos®Controller for Android, “Sonos® Controller for Mac or PC,” which areoffered by Sonos, Inc. of Santa Barbara, Calif. The flexibility of suchan application and its ability to be ported to a new type of portabledevice is advantageous.

Referring back to the system configuration 100 of FIG. 1, a particularzone may contain one or more zone players. For example, the family roomof FIG. 1 contains two zone players 106 and 108, while the kitchen isshown with one zone player 102. Zones may be dynamically configured bypositioning a zone player in a room or space and assigning via thecontroller 130 the zone player to a new or existing zone. As such, zonesmay be created, combined with another zone, removed, and given aspecific name (e.g., “Kitchen”), if so programmed. The zone players 102to 124 are coupled directly or indirectly to a data network, such as thedata network 128 shown in FIG. 1. The data network 128 is represented byan octagon in the figure to stand out from other components shown in thefigure. While the data network 128 is shown in a single location, it isunderstood that such a network may be distributed in and around thesystem configuration 100.

Particularly, the data network 128 may be a wired network, a wirelessnetwork, or a combination of both. In some embodiments, one or more ofthe zone players 102-124 are wirelessly coupled to the data network 128based on a proprietary mesh network. In some embodiments, one or more ofthe zone players 102-124 are wirelessly coupled to the data network 128using a non-mesh topology. In some embodiments, one or more of the zoneplayers 102-124 are coupled via a wire to the data network 128 usingEthernet or similar technology. In addition to the one or more zoneplayers 102-124 connecting to the data network 128, the data network 128may further allow access to a wide area network, such as the Internet.

In certain embodiments, the data network 128 may be created byconnecting any of the zone players 102-124, or some other connectingdevice, to a broadband router. Other zone players 102-124 may then beadded wired or wirelessly to the data network 128. For example, a zoneplayer (e.g., any of zone players 102-124) may be added to the systemconfiguration 100 by simply pressing a button on the zone player itself,which enables a connection to be made to the data network 128. Thebroadband router may be connected to an Internet Service Provider (ISP),for example. The broadband router may be used to form another datanetwork within the system configuration 100, which may be used in otherapplications (e.g., web surfing). The data network 128 may also be usedin other applications, if so programmed. Further, in certainembodiments, the data network 128 is the same network used for otherapplications in the household.

In certain embodiments, each zone can play from the same audio source asanother zone or each zone can play from a different audio source. Forexample, someone can be grilling on the patio and listening to jazzmusic via zone player 124, while someone is preparing food in thekitchen and listening to classical music via zone player 102. Further,someone can be in the office listening to the same jazz music via zoneplayer 110 that is playing on the patio via zone player 124. In someembodiments, the jazz music played via zone players 110 and 124 isplayed in synchrony. Synchronizing playback amongst zones allows forsomeone to pass through zones while seamlessly listening to the audio.Further, zones may be put into a “party mode” such that all associatedzones will play audio in synchrony.

In certain embodiments, a zone contains two or more zone players. Forexample, the family room contains two zone players 106 and 108, and thehome theater room contains at least zone players 116, 118, and 120. Azone may be configured to contain as many zone players as desired, andfor example, the home theater room might contain additional zone playersto play audio from a 5.1 channel or greater audio source (e.g., a movieencoded with 5.1 or greater audio channels). If a zone contains two ormore zone players, such as the two zone players 106 and 108 in thefamily room, then the two zone players 106 and 108 may be configured toplay the same audio source in synchrony, or the two zone players 106 and108 may be paired to play two separate sounds in left and rightchannels, for example. In other words, the stereo effects of a sound maybe reproduced or enhanced through the two zone players 106 and 108, onefor the left sound and the other for the right sound. In certainembodiments, paired zone players may play audio in synchrony with otherzone players.

In certain embodiments, three or more zone players may be configured toplay various channels of audio that is encoded with three channels ormore sound. For example, the home theater room shows zone players 116,118, and 120. If the sound is encoded as 2.1 channel audio, then thezone player 116 may be configured to play left channel audio, the zoneplayer 118 may be configured to play right channel audio, and the zoneplayer 120 may be configured to play bass frequencies. Otherconfigurations are possible and depend on the number of zone players andthe type of audio. Further, a particular zone may be configured to playa 5.1 channel audio in one instance, such as when playing audio from amovie, and then dynamically switch to play stereo, such as when playingaudio from a two channel source.

In certain embodiments, two or more zone players may be sonicallyconsolidated to form a single, consolidated zone player. A consolidatedzone player (though made up of multiple, separate devices) may beconfigured to process and reproduce sound differently than anunconsolidated zone player or zone players that are paired, because aconsolidated zone player will have additional speaker drivers from whichsound may be passed. The consolidated zone player may further be pairedwith a single zone player or yet another consolidated zone player. Eachplayback device of a consolidated playback device is preferably set in aconsolidated mode.

According to some embodiments, one can continue to do any of: group,consolidate, and pair zone players, for example, until a desiredconfiguration is complete. The actions of grouping, consolidation, andpairing are preferably performed through a control interface, such asusing controller 130, and not by physically connecting and re-connectingspeaker wire, for example, to individual, discrete speakers to createdifferent configurations. As such, certain embodiments described hereinprovide a more flexible and dynamic platform through which soundreproduction can be offered to the end-user.

Sources of audio content to be played by zone players 102-124 arenumerous. Music from a personal library stored on a computer ornetworked-attached storage (NAS) may be accessed via the data network128 and played. Internet radio stations, shows, and podcasts may beaccessed via the data network 128. Music services that let a user streamand download music and audio content may be accessed via the datanetwork 128. Further, music may be obtained from traditional sources,such as a turntable or CD player, via a line-in connection to a zoneplayer, for example. Audio content may also be accessed through AirPlay™wireless technology by Apple, Inc., for example. Audio content receivedfrom one or more sources may be shared amongst the zone players 102 to124 via the data network 128 and/or the controller 130.

III. Example Playback Device

Referring now to FIG. 4, there is shown an example functional blockdiagram of a zone player 400 in accordance with an embodiment. The zoneplayer 400 of FIG. 4 includes a network interface 402, a processor 408,a memory 410, an audio processing component 412, a module 414, an audioamplifier 416, and a speaker unit 418 coupled to the audio amplifier416. FIG. 2A shows an example illustration of such a zone player. Othertypes of zone players may not include the speaker unit 418 (e.g., suchas shown in FIG. 2B) or the audio amplifier 416 (e.g., such as shown inFIG. 2C). Further, it is contemplated that the zone player 400 may beintegrated into another component. For example, the zone player 400could be constructed as part of a lamp for indoor or outdoor use.

Referring back to FIG. 4, the network interface 402 facilitates a dataflow between zone players and other devices on a data network (e.g., thedata network 128 of FIG. 1) and the zone player 400. In someembodiments, the network interface 402 may manage the assembling of anaudio source or file into smaller packets that are to be transmittedover the data network or reassembles received packets into the originalsource or file. In some embodiments, the network interface 402 mayfurther handle the address part of each packet so that it gets to theright destination or intercepts packets destined for the zone player400. Accordingly, in certain embodiments, each of the packets includesan Internet Protocol (IP)-based source address as well as an IP-baseddestination address.

In some embodiments, the network interface 402 may include one or bothof a wireless interface 404 and a wired interface 406. The wirelessinterface 404, also referred to as an RF interface, provides networkinterface functions for the zone player 400 to wirelessly communicatewith other devices (e.g., other zone player(s), speaker(s), receiver(s),component(s) associated with the data network 128, etc.) in accordancewith a communication protocol (e.g., any of the wireless standards IEEE802.11a, 802.11b, 802.11g, 802.11n, or 802.15). To receive wirelesssignals and to provide the wireless signals to the wireless interface404 and to transmit wireless signals, the zone player 400 of FIG. 4includes one or more antennas 420. The antenna(s) 420 are discussed ingreater detail below in connection with FIGS. 6A and 6B. The wiredinterface 406 provides network interface functions for the zone player400 to communicate over a wire with other devices in accordance with acommunication protocol (e.g., IEEE 802.3). In some embodiments, a zoneplayer includes both of the interfaces 404 and 406. In some embodiments,a zone player 400 includes only the wireless interface 404 or the wiredinterface 406.

In some embodiments, the processor 408 is a clock-driven electronicdevice that is configured to process input data according toinstructions stored in memory 410. The memory 410 is data storage thatmay be loaded with one or more software modules 414, which can beexecuted by the processor 408 to achieve certain tasks. In theillustrated embodiment, the memory 410 is a tangible machine readablemedium storing instructions that can be executed by the processor 408.In some embodiments, a task might be for the zone player 400 to retrieveaudio data from another zone player or a device on a network. In someembodiments, a task might be for the zone player 400 to send audio datato another zone player or device on a network. In some embodiments, atask might be for the zone player 400 to synchronize playback of audiowith one or more additional zone players. In some embodiments, a taskmight be to pair the zone player 400 with one or more zone players tocreate a multi-channel audio environment. Additional or alternativetasks may be achieved via the one or more software modules 414 and theprocessor 408.

The audio processing component 412 may include one or moredigital-to-analog converters (DAC), an audio preprocessing component, anaudio enhancement component or a digital signal processor, and so on. Incertain embodiments, the audio that is retrieved via the networkinterface 402 is processed and/or intentionally altered by the audioprocessing component 210. Further, the audio processing component 412may produce analog audio signals. The processed analog audio signals arethen provided to the audio amplifier 416 for play back through speakers418. In addition, the audio processing component 412 may includenecessary circuitry to process analog or digital signals as inputs toplay from zone player 400, send to another zone player on a network, orboth play and send to another zone player on the network. An exampleinput includes a line-in connection (e.g., an auto-detecting 3.5 mmaudio line-in connection).

The audio amplifier 416 is a device that amplifies audio signals to alevel for driving one or more speakers 418. The one or more speakers 418may include an individual transducer (e.g., a “driver”) or a completespeaker system that includes an enclosure including one or more drivers.A particular driver may be a subwoofer (for low frequencies), amid-range driver (middle frequencies), and a tweeter (high frequencies),for example. An enclosure may be sealed or ported, for example.

A zone player 400 may also be referred to herein as a playback device.An example playback device includes a Sonos® S5, which is manufacturedby Sonos, Inc. of Santa Barbara, Calif. The S5 is an example zone playerwith a built-in amplifier and speakers. In particular, the S5 is afive-driver speaker system that includes two tweeters, two mid-rangedrivers, and one subwoofer. When playing audio content via the S5, theleft audio data of a track is sent out of the left tweeter and leftmid-range driver, the right audio data of a track is sent out of theright tweeter and the right mid-range driver, and mono bass is sent outof the subwoofer. Further, both mid-range drivers and both tweeters havethe same equalization (or substantially the same equalization). That is,they are both sent the same frequencies, just from different channels ofaudio. Audio from Internet radio stations, online music and videoservices, downloaded music, analog audio inputs, television, DVD, and soon may be played from a Sonos® S5. While the S5 is an example of a zoneplayer with speakers, it is understood that a zone player with speakersis not limited to one with a certain number of speakers (e.g., fivespeakers as in the S5), but rather can contain one or more speakers.Further, a zone player may be part of another device, which might evenserve a purpose different than audio (e.g., a lamp).

IV. Example Controller

Referring now to FIG. 5, there is shown an example controller 500, whichmay correspond to the controlling device 130 in FIG. 1. The controller500 may be used to facilitate the control of multi-media applications,automation and others in a system. In particular, the controller 500 isconfigured to facilitate a selection of a plurality of audio sourcesavailable on the network and enable control of one or more zone players(e.g., the zone players 102-124 in FIG. 1) through a wireless networkinterface 508. According to one embodiment, the wireless communicationis based on an industry standard (e.g., infrared, radio, wirelessstandards IEEE 802.11a, 802.11b 802.11g, 802.11n, or 802.15). Further,when a particular audio is being accessed via the controller 500 orbeing played via a zone player, a picture (e.g., album art) or any otherdata, associated with the audio source may be transmitted from a zoneplayer or other electronic device to the controller 500 for display.

The controller 500 is provided with a screen 502 and an input interface514 that allows a user to interact with the controller 500, for example,to navigate a playlist of many multimedia items and to controloperations of one or more zone players. The screen 502 on the controller500 may be an LCD screen or a touchscreen, for example. The screen 500communicates with and is commanded by a screen driver 504 that iscontrolled by a microcontroller (e.g., a processor) 506.

The controller 500 includes a network interface 508 that facilitateswireless communication with a zone player. In some embodiments, thecommands such as volume control and audio playback synchronization aresent via the network interface 508. In some embodiments, a saved zonegroup configuration is transmitted between a zone player and acontroller via the network interface 508. There may be more than onecontroller for a particular system. Further, a controller may beintegrated into a zone player.

In certain embodiments, a user may create a zone group including atleast two zone players from the controller 500. The zone players in thezone group may play audio in a synchronized fashion, such that all ofthe zone players in the zone group play back an identical audio sourceor a list of identical audio sources in a synchronized manner such thatno (or substantially no) audible delays or hiccups could be heard.Similarly, in some embodiments, when a user increases the audio volumeof the group from the controller 500, the signals or data of increasingthe audio volume for the group are sent to one of the zone players andcauses other zone players in the group to be increased together involume.

A user via the controller 500 may group zone players into a zone groupby activating a “Link Zones” or “Add Zone” soft button, or de-grouping azone group by activating an “Unlink Zones” or “Drop Zone” button. Forexample, one mechanism for ‘joining’ zone players together for audioplay back is to link a number of zone players together to form a group.To link a number of zone players together, a user may manually link eachzone player or room one after the other. For example, assume that thereis a multi-zone system that includes the following zones: Bathroom,Bedroom, Den, Dining Room, Family Room, and Foyer.

In certain embodiments, a user can link any number of zone players(e.g., the zone players 102-124 of FIG. 1), for example, by startingwith a single zone and then manually linking each zone to that zone. Incertain embodiments, a set of zones can be dynamically linked togetherusing a command to create a zone scene or theme (subsequent to firstcreating the zone scene). For instance, a “Morning” zone scene commandmay link the Bedroom, Office, and Kitchen zones together in one action.Without this single command, the user would need to manually andindividually link each zone. The single command might include a mouseclick, a double mouse click, a button press, a gesture, or some otherprogrammed action. Other kinds of zone scenes may be programmed.

In certain embodiments, a zone scene may be triggered based on time(e.g., an alarm clock function). For instance, a zone scene may be setto apply at 8:00 am. The system can link appropriate zonesautomatically, set specific music to play, and then stop the music aftera defined duration. Although any particular zone may be triggered to an“On” or “Off” state based on time, for example, a zone scene enables anyzone(s) linked to the scene to play a predefined audio (e.g., afavorable song, a predefined playlist) at a specific time and/or for aspecific duration. If, for any reason, the scheduled music failed to beplayed (e.g., an empty playlist, no connection to a share, failedUniversal Plug and Play (UPnP), no Internet connection for an InternetRadio station, etc.), a backup buzzer may be programmed to sound. Thebuzzer may include a sound file that is stored in a zone player, forexample.

The memory 510 may be loaded with one or more application modules 512that can be executed by the microcontroller 506 with or without a userinput via the user interface 514 to achieve certain tasks. In operation,when the microcontroller 506 executes one or more of the applicationmodules 512, the screen driver 504 generates control signals to drivethe screen 502 to display an application specific user interfaceaccordingly. In some embodiments, a first one of the applicationmodule(s) 512 is configured to facilitate grouping a number of selectedzone players into a zone group and synchronizing the zone players foraudio play back. In some embodiments, a second one of the applicationmodule(s) 512 is configured to control the audio sounds (e.g., volume)of the zone players in a zone group.

In the illustrated example of FIG. 5, the application module(s) 512include a control context module 516 constructed in accordance with theteachings of this disclosure. The example control context module 516manages a plurality of control contexts, each corresponding to a mode inwhich the controller 500 controls a specific zone or zone group. Forexample, the control context module 516 manages a first control contextfor the controller 500 in which the controller 500 is configured tocontrol (e.g., determine which media is output by a correspondingplayback device) a first zone defined to include the patio of theexample system 100 of FIG. 1. At the same time, the control contextmodule 516 manages a second control context for the controller 500 inwhich the controller 500 is configured to control (e.g., determine whichmedia is output by a corresponding playback device) a second zonedefined to include the family room of the example system 100 of FIG. 1.The example control context module 516 implements a user interface (or aportion thereof) to be displayed on the screen 502 and detects a changein the control contexts (e.g., communicated to the controller 500 viathe input interface 514) made by a user via the user interface. Inresponse, the example control context module 516 configures thecontroller 500 to operate in a selected control context. In doing so,the control context module 516 determines which physical devices (e.g.,zone players and/or playback devices) of the example system 100 arecurrently controlled by the controller 500. In other words, using thecontrol context module 516 of FIG. 5, the controller 500 controls one ormore zone players, such as the zone players 102-124 of FIG. 1, dependingon which control context the controller 500 a user has selected. Theexample control context module 516 is described in detail below inconnection with FIGS. 6-9.

In the illustrated example of FIG. 5, the application module(s) 512 alsoinclude a queue position placement (QPP) module 518 constructed inaccordance with the teachings of this disclosure. The example QPP module518 manages a location at which a media item is positioned within aqueue when being added to the queue. The example QPP module 518 providesa user interface (or at least a portion thereof) with a plurality ofdrop zones into which a media item (e.g., an icon representing a mediaitem) can be dragged and dropped. Each of the drop zones defines aposition in which a queue that the media item is to be placed when themedia item is dropped into the respective drop zone. Thus, depending onwhich of the drop zones the media item is dropped, the example QPPmodule 518 places the media item in the queue in a correspondingposition. The example QPP module 518 is described in detail below inconnection with FIGS. 10-17.

It should be noted that other network-enabled devices such as aniPhone®′ iPad® or any other smart phone or network-enabled device (e.g.,a networked computer such as a PC or Mac® may also be used as acontroller) may be used as a controller to interact or control zoneplayers in a particular environment. In such instances, the applicationmodule(s) 512, including the example control context module 516 and/orthe example QPP module 518, may be implemented in connection with anapplication or program downloaded or otherwise executed by the networkenabled device(s) (e.g., an iPhone® iPad® or any other smart phone ornetwork-enabled device). In some embodiments, a software application orupgrade may be downloaded onto a network enabled device to perform thefunctions disclosed herein.

V. Changing a Control Context on a Controller

An example apparatus that may be used to implement the example controlcontext module 516 of FIG. 5 is illustrated in FIG. 6. Generally, theexample control context module 516 of FIG. 6 enables a user of a touchscreen interface to quickly and efficiently change between controlcontexts of a controller (e.g., the example controller 500 of FIG. 5)associated with the control context module 516. In other words, theexample control context module 516 of FIG. 6 enables the user of thetouch screen interface to quickly and efficiently change which of aplurality of zones and/or devices are controlled by the controller 500.In previous systems, the user was required to navigate through multiplescreens and make multiple selections to make such a change (ifavailable). The example control context module 516 disclosed hereinprovides a mechanism and/or technique that alters a control context ofthe controller 500 using a single swipe of a designated area of a touchscreen of the controller 500. Thus, with a single interaction with thescreen 502 of the controller 500, the control context module 516disclosed herein changes which physical devices (e.g., zone player(s)and/or playback device(s)) are controlled by the controller 500.

The example control context module 516 of FIG. 6 includes a userinterface communicator 600. The user interface communicator 600interacts with or may be integrated with a user interface of thecontroller 500, such as a user interface providing input to the inputinterface 514 of FIG. 5. The user interface communicator 600 enables thecontrol context module 516 to receive information regarding such inputs.Additionally or alternatively, the user interface communicator 600designates a portion of a display to be presented on the screen 502 tobe associated with the control context module 516. In the illustratedexample, the user interface communicator 600 designates a Now Playingsection of a user interface implemented by the controller 500 for aninput that would change the control context of the controller 500. FIG.7 is a screenshot 700 of an example user interface that may beimplemented by the controller 500 and/or into which the user interfacecommunicator 600 of FIG. 6 may be integrated. The example Now Playingsection 702 of FIG. 7 includes information related to a mediapresentation (e.g., output of an audio track) being presented in aparticular zone of, for example, the system 100 of FIG. 1. That is, theNow Playing section 702 describes (e.g., via information related tometadata) media that is playing in a zone (e.g., the living room of thesystem 100 of FIG. 1). A name of the current zone is displayed in theNow Playing section 702. In FIG. 7, the current zone is named LivingRoom.

The user interface communicator 600 receives information related tointeractions between a user and the Now Playing section 702 and providesthe received information to a swipe detector 602. The swipe detector 602interprets information received via the user interface communicator 600to determine whether the user has swiped the touch screen. Such an inputis understood by the user to change control contexts of the controller500. As described above, a control context refers to a mode of thecontroller 500 indicative of which of a plurality of physical devices(e.g., zone players and/or playback devices) are currently controlled bythe controller 500. The control context in which the controller 500 isin at a give point in time is reflected in the Now Playing section 702.When a user wants to, for example, configure a zone not associated witha current control context (e.g., a different zone than the Living Roomzone shown in FIG. 7), the user performs a swiping motion in the NowPlaying section 702 to enter the controller 500 into a control contextassociated with the zone to be configured. The swipe detector 602 iscapable of detecting such a swipe and in which direction (e.g., right orleft) the swipe occurred.

When the swipe detector 602 determines that a swipe has occurred in theNow Playing section 702 (e.g., based on information received via theuser interface communicator 600), the swipe detector informs an analyzer604 that a swipe has occurred and provides a direction of the swipe tothe analyzer 604. The example analyzer 604 determines which controlcontext the controller 500 was in prior to the detected swipe byreferencing a current context tracker 606. The current context tracker606 may be a memory location that indicates which control context thecontroller 500 is in and, thus, which zone of the system 100 iscurrently being controlled by the controller 500. The example currentcontext tracker 606 includes an identifier of which zone the controller500 is currently controlling. However, the information defining whichphysical devices (e.g., zone players and/or playback devices) are ineach zone or control context is stored in a control context definitionsdatabase 608. The example database 608 also includes an order in whichthe control contexts are to be displayed on the user interface of thecontroller 500. This order may be stored as a list in the database 608.In the example of FIG. 7, the Living Room zone/control context is firstin the list, a Patio zone/control context is second in the list, etc. Acurrent position in the list is reflected in an indicator 704 in the NowPlaying section 702 of FIG. 7.

The analyzer 604 uses the information from the current context tracker606, the direction of the swipe, and the list of the database 608 todetermine in which control context the detected swipe placed thecontroller 500. For example, when the current control context is theLiving Room context shown in FIG. 7 that is first in the list, the swipedetector 602 detects a leftwards swipe in the Now Playing section 702,and the Patio context is second in the list, the analyzer 604 determinesthat the controller 500 is to change from the Living Room context to thePatio context. Such a change alters the controller 500 to control thephysical devices associated with the Patio zone (e.g., the zone player124 of FIG. 1). As a result, buttons of a Button Bar section 706 willcontrol the physical devices associated with the Patio zone.

When the analyzer determines that such a change in control contextsoccurred, a context changer 610 changes the control context of thecontroller 500. For example, the context changer 610 alters whichcontext identifier is stored in the current context tracker 606.Additionally, the context changer 610 makes any necessary changes tosetting(s) the microcontroller 506 that dictate which physical devicesthe controller 500 is configured to communicate with. Additionally, thecontext changer 610 cooperates with the user interface communicator 600to change the content of the Now Playing section 702 to reflect thenewly entered control context. FIG. 8 is a series of screenshots showingan animated transition from one control context to another in the NowPlaying section 702. In particular, a first screenshot 800 shows the NowPlaying section 702 when the controller 500 is in a first controlcontext corresponding to a Family Room zone. The swipe detector 602detects a leftwards swipe in the Now Playing section 702 and, as shownin a second screenshot 802, the Now Playing section 702 transitions froma first display corresponding to the first control context to a seconddisplay corresponding to the next control context (as determined by theanalyzer 604). A third screenshot 804 shows the Now Playing section 702including information related to the next control context, which in theexample of FIG. 8 corresponds to a Living Room zone. Thus, when thethird screenshot 804 is displayed in the Now Playing section 702, thecontroller 500 is in a second control context and, thus, controls thephysical devices of the Living Room zone. As shown in the thirdscreenshot 804, the indicator 704 of the Now Playing section 702 changesto indicate the newly entered position in the list of the database 608.The indicator 704 indicates how many control context(s) are availableand whether the additional control contexts can be reached if traversingright or left. In some examples, an end of the list may be linked to abeginning of the list, thereby enabling a wrap around scroll function.

Further, the screenshots 800-804 of FIG. 8 demonstrate that a Queuesection 708 adjacent to the Now Playing section 702 also transitionsduring the change of control contexts. In the illustrated example, theQueue section 708 reflects a list of media items to be presented by thedevices (e.g., zone players and/or playback devices) in the zone shownin the Now Playing section 702. The example Queue section 708 isdescribed in greater detail below. Additionally, the screenshots 800-804of FIG. 8 demonstrate that a Tab Bar section 710 adjacent the Queuesection 708 does not transition during the change of control contexts.In the illustrated example, the Tab Bar section 710 provides access tosecondary functionality such as settings, a sleep timer, alarms, and/orany other suitable functionality Like the Tab Bar section 710, theButton Bar section 706 does not transition during the change of controlcontexts. The Tab Bar section 710 and the Button Bar section 706 do nottransition because, for example, the functionality of the buttonsthereon are respectively universal to the different control contexts.

FIG. 9 is a flow diagram representative of example machine readableinstructions that may be executed to implement the example controlcontext module 516 of FIGS. 5 and/or 6. The control context module 516is active in response to, for example, a powering on of the controller500 (block 900). While active, the control context module 516 monitors adesignated area of a user interface for a swiping motion across a touchscreen (block 902). In particular, the user interface communicator 600provides information regarding interactions with a user interface of thecontroller 500 to the swipe detector 602. The swipe detector 602determines whether any of the interactions with the controller userinterface is a swipe in the designated area (e.g., the Now Playingsection 702 of FIG. 7) (block 904).

When the swipe detector 602 determines that a swipe has occurred, theanalyzer 604 determines a current control context of the controller 500(block 906). To do so, the analyzer 604 references the current contexttracker 606, which stores an identifier associated with the currentlycontrolled zone. Further, the analyzer 604 references the controlcontext definitions database 608 to identify a new control context intowhich the detected swipe moved the controller 500 (block 908). Inparticular, the analyzer 604 uses a direction of the detected swipe(e.g., as provided by the swipe detector 602) and a list of the database608 to determine which control context the swipe was towards.

The control context changer 610 changes the control context is which thecontroller 500 is operating (block 910). In the illustrated example, thecontrol context changer 610 makes this change by altering setting(s) inthe microcontroller 506. In some examples, the control context changer610 makes this change via additional or alternative changes and/orinteractions with the controller 500. Control then returns to block 902to detect additional swipes in the designated area.

VI. Queue Position Placement

An example apparatus that may be used to implement the example queueposition placement (QPP) module 518 of FIG. 5 is illustrated in FIG. 10.Generally, the example QPP module 518 of FIG. 10 enables a user of atouch screen interface to utilize a plurality of previously unavailabletechniques to place a media item in a queue (e.g., the example Queuesection 708 of FIG. 7 associated with the controller 500 of FIG. 5). Inprevious systems, the user was required to scroll through potentiallylong queues to place a media item in a desired position. The example QPPmodule 518 disclosed herein enables the user to avoid such tediousscrolling by providing one or more drop areas into which a media itemmay be dragged and dropped. Additionally or alternatively, the exampleQPP module 518 disclosed herein enables the user to avoid tediousscrolling by providing one or more hover areas on which a media item maybe dragged and held. Each drop area and hover area defined by the QPPmodule 518 has a rule that controls a placement of the media item intothe Queue section 708 and/or an action to be taken by the Queue section708 (e.g., accelerating scrolling). A rule may cause, for example, anymedia items dropped into a drop area to be automatically placed at apredetermined position within the Queue section 708. Thus, the QPPmodule 518 enables the user to place the media item at a predeterminedposition with a single interaction with the screen 502 of the controller500 without having to scroll through the Queue section 708. Additionallyor alternatively, a rule may cause, for example, a queue of the Queuesection 708 to be rapidly scrolled, thereby providing quicker access toportions of the queue.

The example QPP module 518 of FIG. 10 includes a user interfacecommunicator 1000. The user interface communicator 1000 is similar tothe user interface 600 of FIG. 6. In particular, the user interfacecommunicator 1000 of FIG. 10 interacts with or may be integrated with auser interface of the controller 500, such as a user interface providinginput to the input interface 514 of FIG. 5. The user interfacecommunicator 1000 enables the QPP module 518 to receive informationregarding such inputs. For example, the user interface communicator 1000receives inputs related to media items being dragging across, held upon,and/or dropped in designated sections of the user interface implementedby the controller 500 such as, for example, the Now Playing section 702and/or the Queue section 708.

The user interface communicator 1000 receives information related toinputs received in connection with the designated sections (e.g., theNow Playing section 702 and/or the Queue section 708) and provides thereceived information to a drop-in detector 1002 and a hover detector1003. The drop-in detector 1002 interprets information received via theuser interface communicator 1000 to determine whether a media item hasbeen dropped into one of the designated sections (e.g., a drop area).The hover detector 1003 interprets information received via the userinterface communicator 1000 to determine whether a media item is beinghovered on one of the designated sections (e.g., a hover area). A mediaitem is dropped into a target section by selecting an icon associatedwith the media item (e.g., by double clicking and holding the icon on atouch screen) from an originating section (e.g., a library), draggingthe icon into the target section, and releasing the icon while the iconhovers over the target section. A media item is hovered on a targetsection by selecting an icon associated with the media item from anoriginating section, dragging the icon onto the target section, andholding the icon on the target section for certain period of time (e.g.,a predetermined amount of time defined to be associated with a hoveringaction). A user drops a media item into the target section when the userdesires to, for example, add the media item to a task or functionalityassociated with the target section. For example, when the user desiresto add a song to a playlist, the user may drag an icon associated withthe song from a Media Source section 712 (FIG. 7) to the Now Playingsection 702 or the Queue section 708. Depending on when the user desiresto listen to the song, the user aims to place the icon in an appropriateposition of the target section. As described below in connection withFIG. 16, a user hovers a media item on a target section when the userdesires to scroll through the queue.

To improve the ability of the user to place a media item in a desiredposition within, for example, the Queue section 708, the example QPPmodule 518 provides a plurality of drop areas, hover areas, andcorresponding rules that automatically place the media item into theQueue section 708 and/or cause the Queue section to automatically takean action. In particular, the QPP module 518 includes a coordinateanalyzer 1004 to determine a location on the screen 502 at which themedia item was dropped and/or hovered (as detected by the drop-indetector 1002 or the hover detector 1003). Different coordinates on thescreen 502 correspond to different drop areas and/or hover areas definedby the QPP module 518. In some examples, one or more drop areas mayoverlap with one or more hover areas. The drop areas and the hover areasand the corresponding coordinates are stored in an area database 1006.When the drop-in detector 1002 or the hover detector 1003 determinesthat a drop-in or hover has occurred, the coordinate analyzer 1004identifies coordinates (e.g., in an X-Y coordinate grid of the screen)at which the media item was dropped or hovered. The coordinate analyzer1004 references an area database 1006 with the coordinates to identify adrop area or hover area of the user interface corresponding to thelocation at which the drop-in or hovering occurred. The area database1006 includes an entry corresponding to the coordinates that defines inwhich of a plurality of drop areas or hover areas the drop-in orhovering, respectively, occurred. Further, that entry of the areadatabase 1006 includes an instruction or definition that dictates how(e.g., where) the media item is to be placed in the Queue section 708and/or an action to be taken by the Queue section 708. In other words,the QPP module 518 places a media item that was dropped into a drop areainto the Queue section 708 in accordance with a predefined orpredetermined positioning rule for that drop area. Further, the QPPmodule 518 causes the Queue section 708 to take one or more predefinedactions in accordance with a corresponding rule when a media item ishovered in a hover area. For the drop areas, the instruction and/ordefinition of the area database 1006 that determines how (e.g., where)the media item is placed into the Queue section 708 is provided to thequeue position placer 1008. The queue position placer 1008 executes theinstruction and/or definition provided by the area database 1006 so thatthe media item is automatically placed in the predetermined orpredefined position of the Queue section 708. Example drop areas andhover areas and example automatic placements and actions for dropped andhovered media items are described below in connection with FIGS. 11-16.

FIG. 11 is a screenshot 1100 of the example Now Playing section 702 ofFIG. 7. In the illustrated example of FIG. 11, the Now Playing section702 defines a drop area into which a media item 1102 can be dropped. Aswith each example described herein, the media item 1102 can be a singlemedia item (e.g., a song) or a collection of media items (e.g., analbum). Also, the media item 1102 can be dragged from any suitablesection of the user interface, such as the Media Source section 712(FIG. 7). In FIG. 11, the media item 1102 is an album that has beendragged from the Media Source section 712, which includes a musiclibrary of media items available to the user of the controller 500. Thelibrary of the Media Source section 712 can include one or more of alocal library of media items, a non-local library of media items, mediaitems from a media service of a cloud, media items listing as searchresults from a query of the cloud service, and/or any other suitablesource of media items available to the controller 500. When the drop-indetector 1002 and the coordinate analyzer 1004 determine that the mediaitem 1102 has been dropped in the Now Playing section 702, a border ofan album artwork portion is highlighted and the controller causes aplayback device to output the media item. Further, when the drop-indetector 1002 and the coordinate analyzer 1004 determine that the mediaitem 1102 has been dropped in the Now Playing section 702, the queueposition placer 1008 places the media item 1102 at the end of a queue inthe Queue section 708. Thus, when the user drags and drops the mediaitem 1102 into the drop area defined as the Now Playing section 702, themedia item 1102 is immediately played by a playback device (e.g., oneassociated with the current control context of the Now Playing section702) and the media item 1102 is placed at the end of the queue to beplayed by that playback device. As a result, the user avoids having totake two actions (e.g., playing the media item and placing the mediaitem in the queue) and having to scroll down to the bottom of the queue,which may be quite lengthy. Instead, a single drop of the media item1102 in the drop area defined by the Now Playing section 702accomplishes the desired results.

FIG. 12 is a screenshot 1200 of the Queue section 708 of FIG. 7. In theexample of FIG. 12, a drop area into which a media item 1202 may bedropped is defined as the right side of the Queue section 708, asdelineated by a border 1204 in FIG. 12. In FIG. 12, the media item 1202is a single media item associated with a song that has been dragged fromthe Media Source section 712. When the drop-in detector 1002 and thecoordinate analyzer 1004 determine that the media item 1202 has beendragged to the right side of the Queue section 708, the border 1204 ishighlighted to inform the user of the borders of the drop area. In FIG.12, the border 1204 defines a top portion of the drop area and a bottomportion of the drop area. The top portion includes an upward arrow 1206and the bottom portion includes a downward arrow 1208. In some examples,the arrows 1206 and 1208 appear in response to the media item 1202 beingdragged into the drop area defined as the right side of the Queuesection 708. When the drop-in detector 1002 and the coordinate analyzer1004 determine that the media item 1202 has been dropped in the topportion of the drop area (e.g., within the top portion of the border1204 or on the upward arrow 1206), the queue position placer 1008 placesthe media item 1202 at the top of a queue in the Queue section 708.Further, when the drop-in detector 1002 and the coordinate analyzer 1004determine that the media item 1202 has been dropped in the bottomportion of the drop area (e.g., within the bottom portion of the border1204 or on the downward arrow 1208), the queue position placer 1008places the media item 1202 at the bottom of a queue in the Queue section708. Thus, when the user drags and drops the media item 1202 into thetop portion or the bottom portion of the drop area defined as the rightside of the Queue section 708, the user avoids having to scroll up tothe top of the queue or down to the bottom of the queue, which may bequite lengthy. Instead, a drop of the media item 1202 anywhere in thetop or bottom portion of the drop area defined by the border 1204accomplishes the desired result. Moreover, the border 1204 and/or thearrows 1206 and 1208 may flash or otherwise be highlighted when, forexample, the media item 1202 is dragged and/or dropped on the arrows1206, 1208 or the border 1204 (e.g., according to a position of acursor) to provide feedback to the user regarding the interaction withthe respective element. In contrast to the example of FIG. 11, the mediaitem is not immediately played when the media item 1202 is dropped inthe drop area shown in FIG. 12, for example.

FIG. 13 is a screenshot 1300 of the Queue section 708 of FIG. 7. In theexample of FIG. 13, a drop area into which a media item 1302 may bedropped is defined as the left side of the Queue section 708, asdelineated by a border 1304 in FIG. 13. In FIG. 13, the media item 1302is a single media item associated with a song that has been dragged fromthe Media Source section 712. When the drop-in detector 1002 and thecoordinate analyzer 1004 determine that the media item 1302 has beendropped in the left side of the Queue section 708, the border 1304 ishighlighted to inform the user of the borders of the drop area. Further,when the drop-in detector 1002 and the coordinate analyzer 1004determine that the media item 1302 has been dropped in the left side ofthe Queue section 708, the queue position placer 1008 places the mediaitem 1302 at a position in the queue at which the media item 1302 isreleased (e.g., dropped). As the user scrolls the media item 1302 up ordown the queue in the drop area defined as the left side of the Queuesection 708, a slot 1306 opens within the queue where the media item1302 is over. In some examples, the slot 1306 opens below the queue itemhaving a boundary box that includes a vertical midpoint of the mediaitem icon, thereby pushing the rest of the queue items downwards. Whenthe user releases the media item 1302, the queue position placer 1008places the media item 1302 in the slot 1306. In the illustrated example,the media item 1302 is not immediately played in response to the mediaitem 1302 being dropped in the drop area of FIG. 13.

FIG. 14 is screenshot 1400 of the Queue section 708 of FIG. 7. Theexample of FIG. 14 is similar to the example of FIG. 13 in that a droparea into which a media item 1402 may be dropped is defined as the leftside of the Queue section 708. While the media 1302 of FIG. 13 is asingle media item, the media item 1402 of FIG. 14 is a collection ofmedia items, such as an album. In such instances, a slot 1404 is createdin the queue of the Queue section 708 and the queue position placer 1008places the collection media item 1402 in the slot 1404. In someexamples, the individual items of the collection of media items fill theslot 1404, which expands to accommodate the media items. When the queueposition placer 1008 places such a collection, a message may bedisplayed (e.g., via the user interface communicator 1002) on the screen502. FIG. 15 is a screenshot 1500 of the Queue section 708 of Figureincluding an example message 1502 indicating that a collection of mediaitems has been added to the queue and a number of individual items thathas been added to the queue.

FIG. 16 is a screenshot 1600 of the Queue section 708 of FIG. 7. In theexample of FIG. 16, two hover areas on which a media item 1602 may behovered are defined as a top 1604 of the Queue section 708 and bottom1606 of the Queue section 708. In FIG. 16, the media item 1602 is asingle media item associated with a song that has been dragged from theMedia Source section 712. When the hover detector 1003 and thecoordinate analyzer 1004 determine that the media item 1602 is beinghovered on the top hover area 1604 for a predetermined amount of time(e.g., one second or three seconds), the queue of the Queue section 708is rapidly scrolled upwards from a current position. If the queue is orhas reached the first item in the queue and the hover detector 1003detects that the user still holds on to the media item 1602, a drop zone(e.g., as shown in FIGS. 13 and 14) appears at the top of the queue andthe media item 1602 is added to the queue at a predetermined position(e.g., at a top spot of the queue). When the hover detector 1003 and thecoordinate analyzer 1004 determine that the media item 1602 is beinghovered on the bottom hover area 1606 for a predetermined amount of time(e.g., one second), the queue of the Queue section 708 is rapidlyscrolled downwards from a current position. If the queue is or hasreached the last item in the queue and the hover detector 1003 detectsthat the user still holds on to the media item 1602, a drop zone appearsat the bottom of the queue and the media item 1602 is added to the queueat a predetermined position (e.g., at a bottom spot of the queue). Insome examples, when the accelerated scroll operation described above isactive (e.g., while the queue is scrolling upwards or downwards), otherindicators (e.g., the arrows 1206 and 1208 of FIG. 12) may be removedfrom the display.

FIG. 17 is a flow diagram representative of example machine readableinstructions that may be executed to implement the example QPP module518 of FIGS. 5 and/or 10. The QPP module 518 is active in response to,for example, a powering-on of the controller 500 (block 1700). Whileactive, the QPP module 518 monitors a designated area of a userinterface (e.g., the Now Playing section 702 of the Queue section 708)for a dropped media item via a touch screen (block 1702). In particular,the user interface communicator 1000 provides information regardinginteractions with a user interface of the controller 500 to the drop-indetector 1002. The drop-in detector 1002 determines whether any of theinteractions with the controller user interface is a drop of a mediaitem in the designated area (block 1704).

When the drop-in detector 1002 determines that a drop-in has occurred,the coordinate analyzer 1004 determines where the drop-in occurred byusing the coordinates corresponding to the drop-in to reference the areadatabase 1006 (block 1706). An entry in the area database 1006associated with the coordinates of the drop-in indicates which (if any)of one or more drop areas the media item was dropped into. The database1006 also includes a placement rule associated with the identified droparea that controls how the dropped media item is to be placed in, forexample, a queue of media items (block 1708). The queue position placer1008 uses the placement rule to place the dropped media item into thequeue in a predetermined position (block 1710). Control then returns toblock 1704.

Various inventions have been described in sufficient detail with acertain degree of particularity. It is understood to those skilled inthe art that the present disclosure of embodiments has been made by wayof examples only and that numerous changes in the arrangement andcombination of parts may be resorted without departing from the spiritand scope of the present disclosure as claimed. While the embodimentsdiscussed herein may appear to include some limitations as to thepresentation of the information units, in terms of the format andarrangement, the embodiments have applicability well beyond suchembodiment, which can be appreciated by those skilled in the art.Accordingly, the scope of the present disclosure is defined by theappended claims rather than the forgoing description of embodiments.

We claim:
 1. A method to be performed by a mobile device, the methodcomprising: displaying, via a touch-screen display of the mobile device,a control application of a media playback system comprising multiplezones, wherein a first zone of the multiple zones includes one or morefirst playback devices and a second zone of the multiple zones includesone or more second playback devices; receiving, via the controlapplication, input data representing a command to display a firstcontrol interface from among multiple control interfaces of the controlapplication, wherein the multiple control interfaces correspond torespective zones, and wherein the multiple control interfaces areconfigured to be displayed substantially full-screen within adisplayable area of the touch-screen display; in response to receivingthe input data to display the first control interface, displaying, viathe touch-screen display of the mobile device, the first controlinterface, wherein the first control interface comprises: (i) agraphical representation of a name of the first zone; (ii) a firstregion comprising (a) transport controls selectable to control playbackby the first zone and (b) a volume control to control volume of the oneor more first playback devices; (iii) a second region comprisinggraphical representations of metadata associated with a first audiotrack in a playback queue of the first zone; and (iv) a graphicalrepresentation of a first position in an ordered list of the multiplezones; while displaying the first control interface, detecting, in thesecond region of the first control interface, touch-input datarepresenting a first swipe input; determining that the first swipe inputis in a first direction corresponding to a subsequent position in theordered list; and in response to receiving the touch-input datarepresenting the first swipe input and determining that the first swipeinput is in the first direction corresponding to the subsequent positionin the ordered list, changing interfaces of the control application fromdisplaying the first control interface to displaying a second controlinterface of the control application, wherein the second controlinterface comprises: (i) a graphical representation of a name of thesecond zone; (ii) a first region comprising (a) transport controlsselectable to control playback by the second zone and (b) a volumecontrol to control volume of the one or more second playback devices;(iii) a second region comprising graphical representations of metadataassociated with a second audio track in a playback queue of the secondzone; and (iv) a graphical representation of a second position in theordered list of the multiple zones.
 2. The method of claim 1, furthercomprising: while displaying the second control interface, detecting, inthe second region of the second control interface, touch-input datarepresenting a second swipe input; determining that the second swipeinput is in the first direction corresponding to a subsequent positionin the ordered list; and in response to receiving the touch-input datarepresenting the second swipe input and determining that the secondswipe input is in the first direction corresponding to the subsequentposition in the ordered list, changing interfaces of the controlapplication from displaying the second control interface to displaying athird control interface of the control application, wherein the secondcontrol interface comprises: (i) a graphical representation of a name ofa zone group comprising a third zone and a fourth zone configured toplay back in synchrony, wherein the third zone includes one or morethird playback devices and the fourth zone includes one or more fourthplayback devices; (ii) a first region comprising (a) transport controlsselectable to control playback by the zone group and (b) a volumecontrol to control volume of the one or more third playback devices andthe one or more fourth playback devices; (iii) a second regioncomprising graphical representations of metadata associated with a thirdaudio track in a playback queue of the zone group; and (iv) a graphicalrepresentation of a third position in the ordered list of the multiplezones.
 3. The method of claim 1, further comprising: while displayingthe second control interface, detecting, in the second region of thesecond control interface, touch-input data representing a second swipeinput; determining that the second swipe input is in a second directioncorresponding to a previous position in the ordered list; and inresponse to receiving the touch-input data representing the second swipeinput and determining that the second swipe input is in the seconddirection corresponding to the previous position in the ordered list,changing interfaces of the control application from displaying thesecond control interface to displaying the first control interface ofthe control application.
 4. The method of claim 1, wherein the firstcontrol interface further comprises a third region comprising agraphical representation of the playback queue of the first zone, andwherein the second control interface further comprises a third regioncomprising a graphical representation of the playback queue of thesecond zone.
 5. The method of claim 4, wherein the third region of thefirst control interface and the third region of the second controlinterface are scrollable via touch input in a vertical direction withinthe third regions.
 6. The method of claim 1, wherein changing interfacesof the control application from displaying the first control interfaceto displaying the second control interface of the control applicationcomprises displaying an animation showing a transition from displayingthe first control interface to displaying the second control interface.7. The method of claim 1, wherein the first control interface and thesecond control interface are displayed in a portrait orientation on thetouch-screen display of the mobile device, and wherein the firstdirection is horizontal relative to the portrait orientation.
 8. Themethod of claim 1, further comprising: before changing interfaces of thecontrol application from displaying the first control interface todisplaying the second control interface of the control application,receiving input data representing a command to play back one or moreparticular audio tracks in the first zone; and based on receiving theinput data representing the command, sending, via a network interface ofthe mobile device to the one or more first playback devices of the firstzone, instructions to play back the one or more particular audio tracks,wherein the one or more first playback devices continue to play back theone or more particular audio tracks after changing interfaces of thecontrol application from displaying the first control interface todisplaying the second control interface of the control application.
 9. Atangible, non-transitory, computer-readable medium storing instructionsthat, when executed by one or more processors, cause a mobile device toperform functions comprising: displaying, via a touch-screen display ofthe mobile device, a control application of a media playback systemcomprising multiple zones, wherein a first zone of the multiple zonesincludes one or more first playback devices and a second zone of themultiple zones includes one or more second playback devices; receiving,via the control application, input data representing a command todisplay a first control interface from among multiple control interfacesof the control application, wherein the multiple control interfacescorrespond to respective zones, and wherein the multiple controlinterfaces are configured to be displayed substantially full-screenwithin a displayable area of the touch-screen display; in response toreceiving the input data to display the first control interface,displaying, via the touch-screen display of the mobile device, the firstcontrol interface, wherein the first control interface comprises: (i) agraphical representation of a name of the first zone; (ii) a firstregion comprising (a) transport controls selectable to control playbackby the first zone and (b) a volume control to control volume of the oneor more first playback devices; (iii) a second region comprisinggraphical representations of metadata associated with a first audiotrack in a playback queue of the first zone; and (iv) a graphicalrepresentation of a first position in an ordered list of the multiplezones; while displaying the first control interface, detecting, in thesecond region of the first control interface, touch-input datarepresenting a first swipe input; determining that the first swipe inputis in a first direction corresponding to a subsequent position in theordered list; and in response to receiving the touch-input datarepresenting the first swipe input and determining that the first swipeinput is in the first direction corresponding to the subsequent positionin the ordered list, changing interfaces of the control application fromdisplaying the first control interface to displaying a second controlinterface of the control application, wherein the second controlinterface comprises: (i) a graphical representation of a name of thesecond zone; (ii) a first region comprising (a) transport controlsselectable to control playback by the second zone and (b) a volumecontrol to control volume of the one or more second playback devices;(iii) a second region comprising graphical representations of metadataassociated with a second audio track in a playback queue of the secondzone; and (iv) a graphical representation of a second position in theordered list of the multiple zones.
 10. The tangible, non-transitory,computer-readable medium of claim 9, wherein the functions furthercomprise: while displaying the second control interface, detecting, inthe second region of the second control interface, touch-input datarepresenting a second swipe input; determining that the second swipeinput is in the first direction corresponding to a subsequent positionin the ordered list; and in response to receiving the touch-input datarepresenting the second swipe input and determining that the secondswipe input is in the first direction corresponding to the subsequentposition in the ordered list, changing interfaces of the controlapplication from displaying the second control interface to displaying athird control interface of the control application, wherein the secondcontrol interface comprises: (i) a graphical representation of a name ofa zone group comprising a third zone and a fourth zone configured toplay back in synchrony, wherein the third zone includes one or morethird playback devices and the fourth zone includes one or more fourthplayback devices; (ii) a first region comprising (a) transport controlsselectable to control playback by the zone group and (b) a volumecontrol to control volume of the one or more third playback devices andthe one or more fourth playback devices; (iii) a second regioncomprising graphical representations of metadata associated with a thirdaudio track in a playback queue of the zone group; and (iv) a graphicalrepresentation of a third position in the ordered list of the multiplezones.
 11. The tangible, non-transitory, computer-readable medium ofclaim 9, wherein the functions further comprise: while displaying thesecond control interface, detecting, in the second region of the secondcontrol interface, touch-input data representing a second swipe input;determining that the second swipe input is in a second directioncorresponding to a previous position in the ordered list; and inresponse to receiving the touch-input data representing the second swipeinput and determining that the second swipe input is in the seconddirection corresponding to the previous position in the ordered list,changing interfaces of the control application from displaying thesecond control interface to displaying the first control interface ofthe control application.
 12. The tangible, non-transitory,computer-readable medium of claim 9, wherein the first control interfacefurther comprises a third region comprising a graphical representationof the playback queue of the first zone, and wherein the second controlinterface further comprises a third region comprising a graphicalrepresentation of the playback queue of the second zone.
 13. Thetangible, non-transitory, computer-readable medium of claim 12, whereinthe third region of the first control interface and the third region ofthe second control interface are scrollable via touch input in avertical direction within the third regions.
 14. The tangible,non-transitory, computer-readable medium of claim 9, wherein changinginterfaces of the control application from displaying the first controlinterface to displaying the second control interface of the controlapplication comprises displaying an animation showing a transition fromdisplaying the first control interface to displaying the second controlinterface.
 15. The tangible, non-transitory, computer-readable medium ofclaim 9, wherein the first control interface and the second controlinterface are displayed in a portrait orientation on the touch-screendisplay of the mobile device, and wherein the first direction ishorizontal relative to the portrait orientation.
 16. The tangible,non-transitory, computer-readable medium of claim 9, wherein thefunctions further comprise: before changing interfaces of the controlapplication from displaying the first control interface to displayingthe second control interface of the control application, receiving inputdata representing a command to play back one or more particular audiotracks in the first zone; and based on receiving the input datarepresenting the command, sending, via a network interface of the mobiledevice to the one or more first playback devices of the first zone,instructions to play back the one or more particular audio tracks,wherein the one or more first playback devices continue to play back theone or more particular audio tracks after changing interfaces of thecontrol application from displaying the first control interface todisplaying the second control interface of the control application. 17.A controller comprising: a touch-screen display; one or more processors;data storage storing instructions that when executed by the one or moreprocessors cause the controller to perform functions comprising:displaying, via the touch-screen display, a control application of amedia playback system comprising multiple zones, wherein a first zone ofthe multiple zones includes one or more first playback devices and asecond zone of the multiple zones includes one or more second playbackdevices; receiving, via the control application, input data representinga command to display a first control interface from among multiplecontrol interfaces of the control application, wherein the multiplecontrol interfaces correspond to respective zones, and wherein themultiple control interfaces are configured to be displayed substantiallyfull-screen within a displayable area of the touch-screen display; inresponse to receiving the input data to display the first controlinterface, displaying, via the touch-screen display, the first controlinterface, wherein the first control interface comprises: (i) agraphical representation of a name of the first zone; (ii) a firstregion comprising (a) transport controls selectable to control playbackby the first zone and (b) a volume control to control volume of the oneor more first playback devices; (iii) a second region comprisinggraphical representations of metadata associated with a first audiotrack in a playback queue of the first zone; and (iv) a graphicalrepresentation of a first position in an ordered list of the multiplezones; while displaying the first control interface, detecting, in thesecond region of the first control interface, touch-input datarepresenting a first swipe input; determining that the first swipe inputis in a first direction corresponding to a subsequent position in theordered list; and in response to receiving the touch-input datarepresenting the first swipe input and determining that the first swipeinput is in the first direction corresponding to the subsequent positionin the ordered list, changing interfaces of the control application fromdisplaying the first control interface to displaying a second controlinterface of the control application, wherein the second controlinterface comprises: (i) a graphical representation of a name of thesecond zone; (ii) a first region comprising (a) transport controlsselectable to control playback by the second zone and (b) a volumecontrol to control volume of the one or more second playback devices;(iii) a second region comprising graphical representations of metadataassociated with a second audio track in a playback queue of the secondzone; and (iv) a graphical representation of a second position in theordered list of the multiple zones.
 18. The controller of claim 17,wherein the functions further comprise: while displaying the secondcontrol interface, detecting, in the second region of the second controlinterface, touch-input data representing a second swipe input;determining that the second swipe input is in the first directioncorresponding to a subsequent position in the ordered list; and inresponse to receiving the touch-input data representing the second swipeinput and determining that the second swipe input is in the firstdirection corresponding to the subsequent position in the ordered list,changing interfaces of the control application from displaying thesecond control interface to displaying a third control interface of thecontrol application, wherein the second control interface comprises: (i)a graphical representation of a name of a zone group comprising a thirdzone and a fourth zone configured to play back in synchrony, wherein thethird zone includes one or more third playback devices and the fourthzone includes one or more fourth playback devices; (ii) a first regioncomprising (a) transport controls selectable to control playback by thezone group and (b) a volume control to control volume of the one or morethird playback devices and the one or more fourth playback devices;(iii) a second region comprising graphical representations of metadataassociated with a third audio track in a playback queue of the zonegroup; and (iv) a graphical representation of a third position in theordered list of the multiple zones.
 19. The controller of claim 17,wherein the functions further comprise: while displaying the secondcontrol interface, detecting, in the second region of the second controlinterface, touch-input data representing a second swipe input;determining that the second swipe input is in a second directioncorresponding to a previous position in the ordered list; and inresponse to receiving the touch-input data representing the second swipeinput and determining that the second swipe input is in the seconddirection corresponding to the previous position in the ordered list,changing interfaces of the control application from displaying thesecond control interface to displaying the first control interface ofthe control application.
 20. The controller of claim 17, wherein thefirst control interface further comprises a third region comprising agraphical representation of the playback queue of the first zone, andwherein the second control interface further comprises a third regioncomprising a graphical representation of the playback queue of thesecond zone.